Doc mech #118
Open
Doc mech #118
+79
−69
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Adamantios
suggested changes
Mar 12, 2025
Comment on lines
-45
to
+46
| **2.** Setting up an EOA account: | ||
| **b.** Click on the account icon, then on “Add account or hardware wallet”, then “Add a new Ethereum account”, provide a name for the account and then click on “Add account”; | ||
|
|
||
| - *Option 1* (manual creation): | ||
| **c.** Select the newly created account and then click on the top-right menu icon and then “Account details”. You can find the private key by clicking “Show private key”. | ||
|
|
||
| **a.** Install browser extension of Metamask and open it; | ||
|
|
||
| **b.** Click on the account icon, then on “Add account or hardware wallet”, then “Add a new Ethereum account”, provide a name for the account and then click on “Add account”; | ||
|
|
||
| **c.** Select the newly created account and then click on the top-right menu icon and then “Account details”. You can find the private key by clicking “Show private key”. | ||
|
|
||
| **d.** Copy this key in the file `ethereum_private_key.txt` in your project folder (do not include any leading or trailing spaces, tabs or newlines or any other character); | ||
|
|
||
| - *Option 2* (using [open-autonomy](https://github.com/valory-xyz/open-autonomy)): | ||
|
|
||
| **a.** Use the following to generate a private key: | ||
| ``` | ||
| autonomy generate-key ethereum -n 1 | ||
| ``` | ||
| This creates a file keys.json in which the private key can be found on the key “private_key”. | ||
| **b.** Copy this key in the file `ethereum_private_key.txt`. | ||
| **d.** Copy this key in the file `ethereum_private_key.txt` in your project folder (do not include any leading or trailing spaces, tabs or newlines or any other character); |
There was a problem hiding this comment.
@Adamantios Only the part which creates the key file with autonomy generate-key ethereum -n 1 is removed (since it is not really needed ?)
Comment on lines
+83
to
+86
| In order to find which tools the Mech uses, click on its service id, and then "View code" in the window which opens. Open the folder `mech` and then `service.yaml`. Copy the IPFS hash which follows `agent: valory/mech:0.1.0` and open the corresponding | ||
| file by going to https://gateway.autonolas.tech/ipfs/ with the copied hash at the end of this address. Open the `mech` folder and then the file `aea-config.yaml`. In this file, the keys of the dictionary `tools_to_package_hash` are the | ||
| names of the tools that this service uses. | ||
|
|
There was a problem hiding this comment.
This is not accurate. The aea config does not contain the tools that the mech is using, it is only a template with default values.
There was a problem hiding this comment.
Probably the best option would be to point to the metadata and make sure that they are always updated.
There was a problem hiding this comment.
@Adamantios Do you suggest that we write a list of metadata hashes in this doc ? (because this is all off-chain)
mariapiamo
reviewed
Mar 12, 2025
docs/mech-client/index.md
Outdated
| ``` | ||
|
|
||
| Replace `<prompt>` by a string which corresponds to the request to send to the Mech, and `<chain-config>` by one of the keys in the dictionary found in the file `.mech_client/configs/mechs.json` (for instance "gnosis"). In the dictionary corresponding to this key, replace the value of `priority_mech_address` with the address of the mech you want to send the request to. | ||
| Change `<bool>` to True in order to use the off-chain method, and False otherwise. | ||
| Change `<bool>` to True in order to use the off-chain method, and False otherwise. Finally, change `<tool>` to the name of the tool you want to use. |
There was a problem hiding this comment.
we should update this when we have a way for say which is the tool that a deployed mech has
There was a problem hiding this comment.
I think we should still specify the tool, since otherwise it does not work (response is invalid).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.